1) Place the RAM Doubler 1.6 Updater on your hard drive.
2) Double-click to launch the Updater.
3) To update the installed RAM Doubler extension - select "Update". The Updater will update the extension to version 1.6 and prompt you to quit when completed. If you received RAM Doubler through the limited-time Microsoft Office 4.2 special promotion, this is all you should do.
4) If you wish to update the RAM Doubler master diskette - it's not necessary to do so - select "Update Master Disk". Unlock your master diskette and insert it into the floppy drive. The Updater will update the Installer to version 1.6 and prompt you to quit when completed. The previous version of the RAM Doubler Installer will be saved in a folder named "old" on the master diskette.
PCI Power Macs (9500, 8500, 7500, 7200) and OpenTransport compatibility is implemented.
PowerBook 5300, PowerBook 190, and Duo 2300 series compatibility is implemented.
Power Mac/Performa 5200/6200 series compatibility is implemented.
Transferring a file to a floppy in DOS mode on the 6100 DOS Compatible now works.
AppleMail enclosures with PowerTalk now transfer correctly.
File transfer over certain LocalTalk configurations now completes. (AppleTalk Users: please read the "AppleTalk Users" section of "Known Incompatibilities" for important information).
A fix for certain Power Mac upgrade cards and Connectix Speed Doubler is implemented.
RAM Doubler 1.6 now has the 'RAM Doubler/Symantec Project Manager 8.0 Patch' built-in, which allows the launching of Symantec Project Manager v8.0 or 8.0.1 with RAM Doubler installed. Previous users of the RAM Doubler/Symantec patch should remove it after installing RAM Doubler 1.6.
FWB SCSI JackHammer compatibility with RAM Doubler is improved.
You can disable all extensions by holding down the shift key at boot (restart) time.
You can disable all extensions except for RAM Doubler by holding down the shift and option keys at boot time.
We strongly suggest you install System 7.5 Update 1.0, which fixes a number of long-standing bugs in the Mac OS and provides some speed improvements. One notable problem in System 7.5 that has been corrected with Update 1.0 is that floppies were not recognized in 24-bit addressing mode with RAM Doubler installed.
Because of the increased system requirements of System 7.5, 8MB of RAM is required for RAM Doubler (and recommended by Apple for System 7.5).
Hewlett Packard (HP) DeskWriter print drivers may exhibit slow performance or failure under extended memory (i.e. while running with either RAM Doubler or Apple virtual memory). Until the problem is fixed, the workarounds we (HP and Connectix) recommend, in order of preference, are 1) turn off the "Background Printing" option (located in the Chooser when selecting DeskWriter); or 2) reduce the amount of free memory before printing by opening several applications so that the "Largest Unused Block" reported by the Finder is smaller (we recommend trying to lower it to below 1500K if you are experiencing this problem).
AppleTalk Users: Make sure you have the latest AppleTalk driver; older versions of AppleTalk have compatibility issues under extended memory (Apple virtual memory or RAM Doubler). Open the Network control panel to check the version of AppleTalk listed. If there is no version listed or the version listed is less than 58.1.5, then AppleTalk should be updated using Network Software Installer, from Apple. The most current version of Network Software Installer is version 1.5.1 and can be obtained from most Apple software sites online or from an Apple Dealer. Note: For PCI Power Macs (7200, 8500, etc.), which use Open Transport and the AppleTalk control panel, the compatibilities issues with extended memory are not applicable.
Accelerators that do not support Apple's Virtual Memory are not compatible with RAM Doubler. These accelerators include:
- Radius Rocket
- Fusion Data System's TokaMac
- Mobius Speedster 040
- Applied Engineering Transwarp
- MicroMac Carrera
Similarly, non-accelerator hardware add-ons that are not compatible with Apple virtual memory may have problems with RAM Doubler as well; all third-party PowerBook display cards, notably the Envisio display adapters, are not compatible with RAM Doubler.
Some hard disk drivers, notably early versions of Alysis' eDisk, allocate memory in a way that prevents RAM Doubler from extending RAM. Contact your hard drive vendor if you receive the alert concerning a driver not in the system heap.
usrEZ's UltraShield and UltraSecure users should update to version 3.52 (for UltraSecure) and 2.52 (for Ultra Shield), or later.
NEC DPI on the Fly users should use version 3.0 or later.
FWB SCSI JackHammer users should disable "use main memory as buffers" in the JackHammer control panel.
The following items are not compatible with extended memory environments (more total memory than built-in memory); therefore, these items are not currently compatible with RAM Doubler or Apple virtual memory:
- Texas Instruments' Paper Tray Manager for microLaser printers
- "AV DSP Power" plug-in for Adobe Photoshop on the 660AV and 840AV
- Around the World in 80 Days CD-ROM
Note: This is not a complete listing of items that do not work with virtual memory, but contains the most common items reported. Anything that is not compatible with Apple virtual memory is not compatible with RAM Doubler.
MacTCP 1.0 and 1.1 are not compatible with RAM Doubler; we suggest upgrading to version 2.0.4 or later which is compatible. As of this writing, MacTCP 2.0.6 is the current version.
Macintosh 660AV or 840AV with System 7.1 users: make sure you have at least version 1.1 of the "Enabler 088" file. Version 1.0 causes problems with the Express Modem when RAM Doubler is installed. You can acquire Enabler 088 version 1.2 by installing System Update 3.0 (for System 7.1) from Apple; or, by upgrading to System 7.5, which has the latest enabler built-in.
In general, you should use the latest System Update from Apple. As of this writing, for System 7.5, this is System 7.5 Update 1.0; for System 7.1 it is System Update 3.0.
RAM Doubler now works better on newer models of Power Mac in addition to Power Mac upgrade cards from Apple and third parties.
RAM Doubler is now compatible with the 603 processor.
RAM Doubler no longer causes folders to appear "missing" on some Macs when Apple CD-ROM 5.0 and file sharing are in use simultaneously.
Certain CD-ROM sound files now play with RAM Doubler installed.
RAM Doubler now recognizes and uses RAM on the DayStar PowerPro accelerator when running in 68K mode.
CHANGES in RAM DOUBLER 1.5.1:
RAM Doubler is now compatible with SCSI Manager 4.3.
RAM Doubler now works better with GeoPort on Power Macs.
An incompatibility with CD AllCache has been worked around.
Using File Sharing on Power Macs is more reliable now.
CHANGES in RAM DOUBLER 1.5:
Compatibility with the Power Macintosh; RAM Doubler now supports Macintoshes equipped with a PowerPC, 68040, 68030, or 68020 (with PMMU) processor.
For the Power Macintosh, file mapping is now implemented. File mapping is a technology which allows for a reduction in memory requirements by using the memory management unit to manage the loading and unloading of native code segments.
RAM Doubler's reliability on 4- and 5-megabyte Macintoshes running in 24-bit addressing mode has been significantly improved.
Many small changes were made for compatibility with Apple System 7.5. Note that RAM Doubler should not be used with the "SCSI Manager 4.3" extension. (See incompatibilities section.)
CHANGES in RAM DOUBLER 1.0.4:
Compatibility with System 6.0.5 and 6.0.7 has been improved.
A problem with improper flushing of the cache on some machines, notably docked 68040-based PowerBook Duos, has been fixed.
CHANGES in RAM DOUBLER 1.0.3:
A problem that affected TMON 3.1 during the boot process is now fixed.
RAM Doubler now works better with System 7.5.
RAM Doubler now works on PowerBooks equipped with a 68040 processor (PowerBook 500 series and Duo 280 & 280c).
CHANGES in RAM DOUBLER 1.0.2:
Various changes were made to improve reliability and speed of networking operations. If you had problems networking over EtherNET, be sure to also use Apple's Network Software Installer 1.4.5 or later.
A bug in the Mac ROM Memory Manager was worked around which could cause system heap corruption at boot time. (i.e., if your Mac hung at "Welcome to Macintosh", it shouldn't anymore under 1.0.2)
A bug in the Mac BlockMove routine on 040s was worked around.
Extremely large reads and writes (more than half of RAM being read or written at once) happening on unfragmented hard disk drives work without hanging now.
RAM Doubler handles unsuccessful calls to the OS routine HoldMemory more reliably.
MachTen and RAM Doubler now work together.
Changes were made to better support NuBus SCSI accelerator cards. RAM Doubler 1.0.2 will be able to work with a future version of the FWB JackHammer.
A hang on startup occuring on some 68040 accelerators for Mac II, IIx, IIcx, or SE/30 has been corrected.
Restarting no longer hangs on a Macintosh LC with a DayStar 040 accelerator. Restarting a II/IIx/IIcx/SE30 with more than 14 megabytes of RAM in 24-bit mode no longer hangs.
RAM Doubler no longer tries to use a CD-ROM or a locked removable drive to store temporary data onto.
RAM Doubler no longer crashes if the "use RAM for ROM" option for the AV Macs is set. Instead it disables itself.
RAM Doubler now detects the 68EC030 processor and disables itself accordingly. (Sorry, without an MMU, RAM Doubler can't function.)
Floating-point processing functions slightly faster on 68040s.
In cases where RAM Doubler must use hard drive space, the speed has been increased, and the disk space has been decreased.
RAM Doubler no longer complains about MacsBug versions 6.5 and greater. RAM Doubler remains incompatible with development releases of 6.3 and 6.4 versions of MacsBug, due to bugs in those versions which cause unreliable tracing and system hangs when run with RAM Doubler. Version 6.2.2 of MacsBug works fine. On a Centris 610, RAM Doubler will make the necessary patches so that 6.2.2 will work on your machine.
Using MacsBug to trace through priveleged instructions works correctly now, tracing only one instruction at a time.
